Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ceef5c2b2394c8b84525d183ff56212cd1fa302ad92c89b2a868d996ca4d9b7

Tx prefix hash: a60585248056fac0ed0d62c89b633916e97a1596a58269150c18c23310fa0927
Tx public key: 71cf78fea736f78772f345b4c06cb98df380f4bc7bfee9d862e4ccadf37a1084
Timestamp: 1723081257 Timestamp [UCT]: 2024-08-08 01:40:57 Age [y:d:h:m:s]: 00:280:15:44:49
Block: 1083093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200507 RingCT/type: yes/0
Extra: 0171cf78fea736f78772f345b4c06cb98df380f4bc7bfee9d862e4ccadf37a108402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d7aeb64a5a259c3efb9c7ecf76cf13c8d3a856bd9afbd59cf2568745c21566 0.600000000000 1556928 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": 1083103, "vin": [ { "gen": { "height": 1083093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d7aeb64a5a259c3efb9c7ecf76cf13c8d3a856bd9afbd59cf2568745c21566" } } ], "extra": [ 1, 113, 207, 120, 254, 167, 54, 247, 135, 114, 243, 69, 180, 192, 108, 185, 141, 243, 128, 244, 188, 123, 254, 233, 216, 98, 228, 204, 173, 243, 122, 16, 132, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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