Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6426085203b97ba1e0f831bb400488b385ab100cb7a33dc6b9c7b6b426b6996

Tx prefix hash: 3d336f21945388f3b6090a13fdb8bc41b18dde98c963c576a74f20fd82a604db
Tx public key: e1ff4bff1bec846df82fdcf35512922f2809a22d668af92359fb0d55812a1a4e
Timestamp: 1749949413 Timestamp [UCT]: 2025-06-15 01:03:33 Age [y:d:h:m:s]: 00:159:16:46:09
Block: 1305213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111891 RingCT/type: yes/0
Extra: 01e1ff4bff1bec846df82fdcf35512922f2809a22d668af92359fb0d55812a1a4e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 202f7e13e15a5ec8e8adc01b2f2ceae5d61c719287a4fc1568c5af8cf8307c1e 0.600000000000 1792812 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": 1305223, "vin": [ { "gen": { "height": 1305213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "202f7e13e15a5ec8e8adc01b2f2ceae5d61c719287a4fc1568c5af8cf8307c1e" } } ], "extra": [ 1, 225, 255, 75, 255, 27, 236, 132, 109, 248, 47, 220, 243, 85, 18, 146, 47, 40, 9, 162, 45, 102, 138, 249, 35, 89, 251, 13, 85, 129, 42, 26, 78, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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