Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba3cd503d568a5a2a97f3d9b62193f04d39408fd7cb7a1ffabeb0fea46a43a3

Tx prefix hash: 76a53687066dda339562bb6dc00a2a2febce46715a0aace47ba781b8b6ad34db
Tx public key: aee82c7fd72dae017ea08712a2672138fbc4b006155ba0b7f859194f8eeccc30
Timestamp: 1737739987 Timestamp [UCT]: 2025-01-24 17:33:07 Age [y:d:h:m:s]: 00:326:21:00:03
Block: 1204429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231203 RingCT/type: yes/0
Extra: 01aee82c7fd72dae017ea08712a2672138fbc4b006155ba0b7f859194f8eeccc300211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbfe596a6af82a0303a9d55b12804fbdcc5b125a2c85ff44cadac5547792bb43 0.600000000000 1691114 of 15

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": 1204439, "vin": [ { "gen": { "height": 1204429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbfe596a6af82a0303a9d55b12804fbdcc5b125a2c85ff44cadac5547792bb43" } } ], "extra": [ 1, 174, 232, 44, 127, 215, 45, 174, 1, 126, 160, 135, 18, 162, 103, 33, 56, 251, 196, 176, 6, 21, 91, 160, 183, 248, 89, 25, 79, 142, 236, 204, 48, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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