Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a87248cd85a913b0d9a16f57227563f7a34397574a346ce84419d1f63f2589

Tx prefix hash: fb1b646b1a7e7399b5e96fbfae430ab74923198f71f6635adef4d03df849c13a
Tx public key: 012945990aa4a2abeb0b1189469e39d1a45e36177d81db1546c5dc2a4ccf85b8
Timestamp: 1736642185 Timestamp [UCT]: 2025-01-12 00:36:25 Age [y:d:h:m:s]: 00:066:21:38:35
Block: 1195384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47612 RingCT/type: yes/0
Extra: 01012945990aa4a2abeb0b1189469e39d1a45e36177d81db1546c5dc2a4ccf85b8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee5898e7cb6ab60c625f500204f0e1cc9031f4f137796996f9820dd00c6e403 0.600000000000 1681973 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": 1195394, "vin": [ { "gen": { "height": 1195384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee5898e7cb6ab60c625f500204f0e1cc9031f4f137796996f9820dd00c6e403" } } ], "extra": [ 1, 1, 41, 69, 153, 10, 164, 162, 171, 235, 11, 17, 137, 70, 158, 57, 209, 164, 94, 54, 23, 125, 129, 219, 21, 70, 197, 220, 42, 76, 207, 133, 184, 2, 17, 0, 0, 0, 3, 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