Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c836018f9afe3bd20847037fb34756f1bcb1f4eacc93bca3bcd38eeaba16173

Tx prefix hash: dbe50694c2a9ad510779c7d27e8ee062775d69185bd03407a582a52d23709246
Tx public key: 5745612ac1f801e536ea28231de247f672d88fb38dd9bf8cb69d079cf01ad6e7
Timestamp: 1705476550 Timestamp [UCT]: 2024-01-17 07:29:10 Age [y:d:h:m:s]: 01:296:22:10:25
Block: 937129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471031 RingCT/type: yes/0
Extra: 015745612ac1f801e536ea28231de247f672d88fb38dd9bf8cb69d079cf01ad6e70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1be13647fb6a0a3c018e7b47cac1b01d93e21a225ac7a6d2ebf3f690e5df089 0.600000000000 1395173 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": 937139, "vin": [ { "gen": { "height": 937129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1be13647fb6a0a3c018e7b47cac1b01d93e21a225ac7a6d2ebf3f690e5df089" } } ], "extra": [ 1, 87, 69, 97, 42, 193, 248, 1, 229, 54, 234, 40, 35, 29, 226, 71, 246, 114, 216, 143, 179, 141, 217, 191, 140, 182, 157, 7, 156, 240, 26, 214, 231, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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