Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cb4a257c93bc36c784ac9cc32b2f6ce23ab7ac2aee733fbb62d7ceb3c755b0f

Tx prefix hash: bc7fba78bd13df06525cf1697d5507bd72c7b044e0d59a6e11b5749553b7e2a4
Tx public key: bb55570307d1e12bdf50dd0be2c4df6d8478b3a19b4e1958da9e41d4bd7f62d5
Timestamp: 1765926462 Timestamp [UCT]: 2025-12-16 23:07:42 Age [y:d:h:m:s]: 00:022:15:27:32
Block: 1435173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16224 RingCT/type: yes/0
Extra: 01bb55570307d1e12bdf50dd0be2c4df6d8478b3a19b4e1958da9e41d4bd7f62d502110000000cd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2b5fa9d6032678ec15b05907ab8c5e24353e61df814cc6f448e24a7335cf670 0.600000000000 1923970 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": 1435183, "vin": [ { "gen": { "height": 1435173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2b5fa9d6032678ec15b05907ab8c5e24353e61df814cc6f448e24a7335cf670" } } ], "extra": [ 1, 187, 85, 87, 3, 7, 209, 225, 43, 223, 80, 221, 11, 226, 196, 223, 109, 132, 120, 179, 161, 155, 78, 25, 88, 218, 158, 65, 212, 189, 127, 98, 213, 2, 17, 0, 0, 0, 12, 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