Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb3c6baac0c5fb8d2430cd62f983cb560fb5273e0b9a85f2e69cba51096c8905

Tx prefix hash: f0ac1fbb8194e07c5b68cd0a51e68e3d6cd63d8722e3db5d18be515bc43db20b
Tx public key: bc40eeea1a62721b6437017b5696f0fdcafd5b88bebd13e8dc6c39a3ed7f34dd
Timestamp: 1737465855 Timestamp [UCT]: 2025-01-21 13:24:15 Age [y:d:h:m:s]: 00:146:08:57:42
Block: 1202161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104372 RingCT/type: yes/0
Extra: 01bc40eeea1a62721b6437017b5696f0fdcafd5b88bebd13e8dc6c39a3ed7f34dd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06f689c4462d0d55c33993c4a1b2890f376c13cd8ec9e2dcef705085de5bca69 0.600000000000 1688822 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": 1202171, "vin": [ { "gen": { "height": 1202161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06f689c4462d0d55c33993c4a1b2890f376c13cd8ec9e2dcef705085de5bca69" } } ], "extra": [ 1, 188, 64, 238, 234, 26, 98, 114, 27, 100, 55, 1, 123, 86, 150, 240, 253, 202, 253, 91, 136, 190, 189, 19, 232, 220, 108, 57, 163, 237, 127, 52, 221, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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