Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1ef15bfa0b3c0432f8799ee4151cc1a86f30722889ffe3cb0178fa46bd32b5

Tx prefix hash: d425d96b4c4ece6a8cb3d9c025ffb6e100afb00cc0694cbecf5f3dfc1004e63c
Tx public key: 0ea39597b1ece01007d1b582949e2ae53924a615b17ea62e3a48526818f80821
Timestamp: 1741342502 Timestamp [UCT]: 2025-03-07 10:15:02 Age [y:d:h:m:s]: 00:300:16:55:20
Block: 1234035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212721 RingCT/type: yes/0
Extra: 010ea39597b1ece01007d1b582949e2ae53924a615b17ea62e3a48526818f80821021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbc64227299ed51d4ecc2f01a01172f3f4b7ba048f5d713bc0ba16bad70e9de0 0.600000000000 1720960 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": 1234045, "vin": [ { "gen": { "height": 1234035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc64227299ed51d4ecc2f01a01172f3f4b7ba048f5d713bc0ba16bad70e9de0" } } ], "extra": [ 1, 14, 163, 149, 151, 177, 236, 224, 16, 7, 209, 181, 130, 148, 158, 42, 229, 57, 36, 166, 21, 177, 126, 166, 46, 58, 72, 82, 104, 24, 248, 8, 33, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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