Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d6f9ce2cbc0219ef9504f6c3c9d12fcd95b956b8b45dd57f35d5699cac1e20

Tx prefix hash: 0ba36e7109db157ee179670cdc232d6b27c4b4ad55b9bfd741d8690ae2f4315d
Tx public key: 53881262e47bb6c1a3769d9cd2695a9189be46d3281a90e74dfbb84faa838f8f
Timestamp: 1723396121 Timestamp [UCT]: 2024-08-11 17:08:41 Age [y:d:h:m:s]: 00:271:19:36:10
Block: 1085712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194174 RingCT/type: yes/0
Extra: 0153881262e47bb6c1a3769d9cd2695a9189be46d3281a90e74dfbb84faa838f8f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a339ce8c535c92f22f23082df479438d3b70fcb5a7a883fe5477d9a4fec2b069 0.600000000000 1560301 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": 1085722, "vin": [ { "gen": { "height": 1085712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a339ce8c535c92f22f23082df479438d3b70fcb5a7a883fe5477d9a4fec2b069" } } ], "extra": [ 1, 83, 136, 18, 98, 228, 123, 182, 193, 163, 118, 157, 156, 210, 105, 90, 145, 137, 190, 70, 211, 40, 26, 144, 231, 77, 251, 184, 79, 170, 131, 143, 143, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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