Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24495a87a040d61ffdd4cd730e2303b5e84a93ca1da34972f0de266729955cb3

Tx prefix hash: 2f144e7f34306c1406c142f911de117a70124fca03d7086b53bda8d7d98a124a
Tx public key: 0829bc13aa5ece0bf5adac5e9e07a49e89c5787fc64cc2dfe20f31e5dc23b1f6
Timestamp: 1761335021 Timestamp [UCT]: 2025-10-24 19:43:41 Age [y:d:h:m:s]: 00:027:19:19:45
Block: 1397140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19880 RingCT/type: yes/0
Extra: 010829bc13aa5ece0bf5adac5e9e07a49e89c5787fc64cc2dfe20f31e5dc23b1f6021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6492acc623a8f7d00acdf7a9fda484d76f7eaea78987e316c651ee606e09beda 0.600000000000 1885431 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": 1397150, "vin": [ { "gen": { "height": 1397140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6492acc623a8f7d00acdf7a9fda484d76f7eaea78987e316c651ee606e09beda" } } ], "extra": [ 1, 8, 41, 188, 19, 170, 94, 206, 11, 245, 173, 172, 94, 158, 7, 164, 158, 137, 197, 120, 127, 198, 76, 194, 223, 226, 15, 49, 229, 220, 35, 177, 246, 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