Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e94439e16fb86e90a1a93ce0266b7068b9a01e601b58413ae7d5393914ad40

Tx prefix hash: 63a74ad55c9bd5be12b4010b88c062e1401320d06ce9451190e41b3d2d481ea5
Tx public key: f5b70f8f6078fdd23a9f459a5e20f81b7d330c39bdc43666a52363c9dfc7e26b
Timestamp: 1760325136 Timestamp [UCT]: 2025-10-13 03:12:16 Age [y:d:h:m:s]: 00:039:14:37:57
Block: 1388755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28349 RingCT/type: yes/0
Extra: 01f5b70f8f6078fdd23a9f459a5e20f81b7d330c39bdc43666a52363c9dfc7e26b021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f012d7d678664cbf11f73d1118875a023f06dc9c1b47c2bae472c895b2b4199 0.600000000000 1876978 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": 1388765, "vin": [ { "gen": { "height": 1388755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f012d7d678664cbf11f73d1118875a023f06dc9c1b47c2bae472c895b2b4199" } } ], "extra": [ 1, 245, 183, 15, 143, 96, 120, 253, 210, 58, 159, 69, 154, 94, 32, 248, 27, 125, 51, 12, 57, 189, 196, 54, 102, 165, 35, 99, 201, 223, 199, 226, 107, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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