Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0769bdf3e05a488393aae720c10dc8dfdd7fcd0e7ee4185b7f723815486146b5

Tx prefix hash: e09ef9915fbe38b978219644dc2dc40887317162d503a9d95207d8b86a34b9c7
Tx public key: 1440b14b6c3a536077fc4c101766acd43b933c2beeed42d943de8c36d9af06e4
Timestamp: 1765729717 Timestamp [UCT]: 2025-12-14 16:28:37 Age [y:d:h:m:s]: 00:008:20:21:20
Block: 1433535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6332 RingCT/type: yes/0
Extra: 011440b14b6c3a536077fc4c101766acd43b933c2beeed42d943de8c36d9af06e4021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5031b4e440949f75f0131f4b7aaa8c3c824af34f25196448ca6c53c1a3c8921b 0.600000000000 1922316 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": 1433545, "vin": [ { "gen": { "height": 1433535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5031b4e440949f75f0131f4b7aaa8c3c824af34f25196448ca6c53c1a3c8921b" } } ], "extra": [ 1, 20, 64, 177, 75, 108, 58, 83, 96, 119, 252, 76, 16, 23, 102, 172, 212, 59, 147, 60, 43, 238, 237, 66, 217, 67, 222, 140, 54, 217, 175, 6, 228, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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