Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a36fefecbcf529b526797fb39c206be573211bada3c0e0c25e56b24563d61b

Tx prefix hash: 792f949bc98d1e4785ab52c2d748c87173f0f2801e3cbc3335300ae1b73ceb42
Tx public key: 8bc21c5b40597011f1d4eaea8d6b5c2c2d6755ef45fc0fc9b36ffbe4c2139e8a
Timestamp: 1762968366 Timestamp [UCT]: 2025-11-12 17:26:06 Age [y:d:h:m:s]: 00:055:04:19:50
Block: 1410661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39510 RingCT/type: yes/0
Extra: 018bc21c5b40597011f1d4eaea8d6b5c2c2d6755ef45fc0fc9b36ffbe4c2139e8a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c3b3ce5523919a88cebce9a01a9a59fb7d209db3440cce8d3d49fd95e27a697 0.600000000000 1899114 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": 1410671, "vin": [ { "gen": { "height": 1410661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c3b3ce5523919a88cebce9a01a9a59fb7d209db3440cce8d3d49fd95e27a697" } } ], "extra": [ 1, 139, 194, 28, 91, 64, 89, 112, 17, 241, 212, 234, 234, 141, 107, 92, 44, 45, 103, 85, 239, 69, 252, 15, 201, 179, 111, 251, 228, 194, 19, 158, 138, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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