Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77057ec0983b9f611bffe72ce3ae6ab3ae7cb45c70f2e4f028d4bdd3a25de1bf

Tx prefix hash: 5cba71f261590ff1512f3d64ad6ea2b351f027253666f21b4c6dc804ee8615dc
Tx public key: 853b1916413d59fd5ec26640e21899f78208a2b3815112d1b2fdc34b463dc194
Timestamp: 1708517027 Timestamp [UCT]: 2024-02-21 12:03:47 Age [y:d:h:m:s]: 01:034:00:03:56
Block: 962360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285303 RingCT/type: yes/0
Extra: 01853b1916413d59fd5ec26640e21899f78208a2b3815112d1b2fdc34b463dc1940211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9ce33125102dd1c9479ffd4ced83df957b43e8c7336814fb4fae00d71816c41 0.600000000000 1421993 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": 962370, "vin": [ { "gen": { "height": 962360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9ce33125102dd1c9479ffd4ced83df957b43e8c7336814fb4fae00d71816c41" } } ], "extra": [ 1, 133, 59, 25, 22, 65, 61, 89, 253, 94, 194, 102, 64, 226, 24, 153, 247, 130, 8, 162, 179, 129, 81, 18, 209, 178, 253, 195, 75, 70, 61, 193, 148, 2, 17, 0, 0, 0, 1, 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