Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4e8b64a01c69468ccc6710f829ee377366ec1d0e2ac3ca5312605fb358d29f

Tx prefix hash: 294f61b1786c90ee7cd574d5c46c34ff7a3922dd4afcbe8779e3a2b079384a53
Tx public key: c0690f79a460444cc34b5b7c2e08b769fe447bb91eaf4dee2db29434f1cfcdec
Timestamp: 1658352769 Timestamp [UCT]: 2022-07-20 21:32:49 Age [y:d:h:m:s]: 03:104:01:44:09
Block: 548109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 854142 RingCT/type: yes/0
Extra: 01c0690f79a460444cc34b5b7c2e08b769fe447bb91eaf4dee2db29434f1cfcdec02110000000acb8520c2000000000000000000

1 output(s) for total of 9.373191439000 dcy

stealth address amount amount idx
00: def65f9b05a7edb39c354089473ca55ca0b02f0f584de706cd6a4345359faedf 9.373191439000 979330 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": 548119, "vin": [ { "gen": { "height": 548109 } } ], "vout": [ { "amount": 9373191439, "target": { "key": "def65f9b05a7edb39c354089473ca55ca0b02f0f584de706cd6a4345359faedf" } } ], "extra": [ 1, 192, 105, 15, 121, 164, 96, 68, 76, 195, 75, 91, 124, 46, 8, 183, 105, 254, 68, 123, 185, 30, 175, 77, 238, 45, 178, 148, 52, 241, 207, 205, 236, 2, 17, 0, 0, 0, 10, 203, 133, 32, 194, 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