Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a40f01ce61f32dc4de82e7e1da207e460e9c5a9aee8708fc42b91cf07866c2

Tx prefix hash: 922f564aa824c48c04df7bfceb3f0bc5cc3f2cb7703efec6967a32fb9e650910
Tx public key: 44f7e84163faeed65c401593d2e70f371926466e66b8c025124003ee8f458211
Timestamp: 1581472882 Timestamp [UCT]: 2020-02-12 02:01:22 Age [y:d:h:m:s]: 05:021:21:59:37
Block: 63081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168501 RingCT/type: yes/0
Extra: 0144f7e84163faeed65c401593d2e70f371926466e66b8c025124003ee8f4582110211000000078a2ee0d9000000000000000000

1 output(s) for total of 379.342270750000 dcy

stealth address amount amount idx
00: e92aff3b13ce7ae1b8954570774d155f406eefd381c58ea0261ca3ae4796320c 379.342270750000 116337 of 0

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": 63091, "vin": [ { "gen": { "height": 63081 } } ], "vout": [ { "amount": 379342270750, "target": { "key": "e92aff3b13ce7ae1b8954570774d155f406eefd381c58ea0261ca3ae4796320c" } } ], "extra": [ 1, 68, 247, 232, 65, 99, 250, 238, 214, 92, 64, 21, 147, 210, 231, 15, 55, 25, 38, 70, 110, 102, 184, 192, 37, 18, 64, 3, 238, 143, 69, 130, 17, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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