Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde8c79e1853cd914519d5f6ccaa8ff5f94f0d768f23b39e04d2f15aac37abcf

Tx prefix hash: 42c2e22a41aeb530bad4fc1aa88b350226cb606bb0489fa96ff4aa03884daafc
Tx public key: e0bb933e94a9d248d3a9b685abe04b50660c8f99ddb7547e7b19cd95fff18606
Timestamp: 1702461218 Timestamp [UCT]: 2023-12-13 09:53:38 Age [y:d:h:m:s]: 01:038:07:09:46
Block: 912170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288675 RingCT/type: yes/0
Extra: 01e0bb933e94a9d248d3a9b685abe04b50660c8f99ddb7547e7b19cd95fff1860602110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ee14f3639feaba7ba8ad048c9ba028e66d1672b195e8dc438dfc17bb9dd79b 0.600000000000 1369390 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": 912180, "vin": [ { "gen": { "height": 912170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ee14f3639feaba7ba8ad048c9ba028e66d1672b195e8dc438dfc17bb9dd79b" } } ], "extra": [ 1, 224, 187, 147, 62, 148, 169, 210, 72, 211, 169, 182, 133, 171, 224, 75, 80, 102, 12, 143, 153, 221, 183, 84, 126, 123, 25, 205, 149, 255, 241, 134, 6, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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