Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 47c345dfbfe4f5ce3bf597232b0f23d9adde9abd6be4dd3654ebd7bd851fac0f

Tx prefix hash: 94ca9a83e63ea769eb491b9652cc17b012ed5df8949c235b8247d2fb91fc5fd8
Tx public key: 800284b50131d06ee5abc8348c63af15ed1807f1a5b93a6f3cedd1044cafc91e
Timestamp: 1660350483 Timestamp [UCT]: 2022-08-13 00:28:03 Age [y:d:h:m:s]: 02:233:01:13:38
Block: 564590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687770 RingCT/type: yes/0
Extra: 01800284b50131d06ee5abc8348c63af15ed1807f1a5b93a6f3cedd1044cafc91e02110000000875e3f0e9000000000000000000

1 output(s) for total of 8.265689146000 dcy

stealth address amount amount idx
00: 74a57b55a31cf63ab142720f6a516fb362e46420c9db91c119d0e93c5577f034 8.265689146000 997436 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 564600, "vin": [ { "gen": { "height": 564590 } } ], "vout": [ { "amount": 8265689146, "target": { "key": "74a57b55a31cf63ab142720f6a516fb362e46420c9db91c119d0e93c5577f034" } } ], "extra": [ 1, 128, 2, 132, 181, 1, 49, 208, 110, 229, 171, 200, 52, 140, 99, 175, 21, 237, 24, 7, 241, 165, 185, 58, 111, 60, 237, 209, 4, 76, 175, 201, 30, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8