Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf6dd589ead23c1ec0c4e08b31596612bc046aa3101b33b7bdb46cc53f60a39

Tx prefix hash: e4309340f9890f0616b3b917902658e97d02084324ebd267852c960d85670202
Tx public key: c8907e41aaf4de8c9c40f24c06b63c0d8db7f8628563cbf6671df871d2443140
Timestamp: 1765086615 Timestamp [UCT]: 2025-12-07 05:50:15 Age [y:d:h:m:s]: 00:014:20:26:11
Block: 1428211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10638 RingCT/type: yes/0
Extra: 01c8907e41aaf4de8c9c40f24c06b63c0d8db7f8628563cbf6671df871d24431400211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e789fbaca084c8bcc8e8aa53c61bf359d5c0fff5a088aed8d26bcaaea96d8f 0.600000000000 1916924 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": 1428221, "vin": [ { "gen": { "height": 1428211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e789fbaca084c8bcc8e8aa53c61bf359d5c0fff5a088aed8d26bcaaea96d8f" } } ], "extra": [ 1, 200, 144, 126, 65, 170, 244, 222, 140, 156, 64, 242, 76, 6, 182, 60, 13, 141, 183, 248, 98, 133, 99, 203, 246, 103, 29, 248, 113, 210, 68, 49, 64, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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