Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 045f0c0d259a3c0ad94a9def3d6c6d68ebf970e1bad4d27604a239f3ac293b90

Tx prefix hash: b2aba51a1bc7f1edbc6db963c229fbd587c42d64d11bc9d82f8ee234db6db594
Tx public key: 8bb6ca6864a8e553518da132a421bb4f9e54e856225bb67a688d7fb5c4c85dcb
Timestamp: 1579943421 Timestamp [UCT]: 2020-01-25 09:10:21 Age [y:d:h:m:s]: 04:339:10:06:42
Block: 52496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132713 RingCT/type: yes/0
Extra: 018bb6ca6864a8e553518da132a421bb4f9e54e856225bb67a688d7fb5c4c85dcb02110000000217786bcf000000000000000000

1 output(s) for total of 411.206327867000 dcy

stealth address amount amount idx
00: fcf0a3845e19b816d4104d900aeedb99607735840e73657bd4f97471e0cf0c9e 411.206327867000 97313 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": 52506, "vin": [ { "gen": { "height": 52496 } } ], "vout": [ { "amount": 411206327867, "target": { "key": "fcf0a3845e19b816d4104d900aeedb99607735840e73657bd4f97471e0cf0c9e" } } ], "extra": [ 1, 139, 182, 202, 104, 100, 168, 229, 83, 81, 141, 161, 50, 164, 33, 187, 79, 158, 84, 232, 86, 34, 91, 182, 122, 104, 141, 127, 181, 196, 200, 93, 203, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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