Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61bfd0fa6a7cdbe305c1704c089afffb1586fe03c2b5af1268c2157f42ebb2d7

Tx prefix hash: c2f278ca53e7ebe5153c7af52ec50645e5dc81168a0ac58d53992224c4a3d289
Tx public key: ee955cfe1eadf81f8214410e66bbe58f4d14ba5f6ee1d365222b72b1363de8b1
Timestamp: 1697559267 Timestamp [UCT]: 2023-10-17 16:14:27 Age [y:d:h:m:s]: 01:169:19:26:15
Block: 871709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382387 RingCT/type: yes/0
Extra: 01ee955cfe1eadf81f8214410e66bbe58f4d14ba5f6ee1d365222b72b1363de8b102110000000533af99f4000000000000000000

1 output(s) for total of 0.793718027000 dcy

stealth address amount amount idx
00: 433f5e0e747e5c9200338d3de7cdf6742c7db560f6d02d978c10d111b06ac1cc 0.793718027000 1326734 of 0

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": 871719, "vin": [ { "gen": { "height": 871709 } } ], "vout": [ { "amount": 793718027, "target": { "key": "433f5e0e747e5c9200338d3de7cdf6742c7db560f6d02d978c10d111b06ac1cc" } } ], "extra": [ 1, 238, 149, 92, 254, 30, 173, 248, 31, 130, 20, 65, 14, 102, 187, 229, 143, 77, 20, 186, 95, 110, 225, 211, 101, 34, 43, 114, 177, 54, 61, 232, 177, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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