Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349045d126b35c0e456ce54e7461d89f7d9f043f30037a057bf479bf09e8a381

Tx prefix hash: 91984d98cacc14aa5d62173bdfdc93ebf8243b484470c91469e2914c2d81d68b
Tx public key: d523f75fe9d43ff0a806b89a8ff03d4d8e26fe909d6f689156a61add3eea6b3b
Timestamp: 1713662880 Timestamp [UCT]: 2024-04-21 01:28:00 Age [y:d:h:m:s]: 00:301:14:47:54
Block: 1005006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215584 RingCT/type: yes/0
Extra: 01d523f75fe9d43ff0a806b89a8ff03d4d8e26fe909d6f689156a61add3eea6b3b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae3c80082d7160cffb03bd466f033d6110e9030edbb2e03dbd45e98bc9028e17 0.600000000000 1465584 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": 1005016, "vin": [ { "gen": { "height": 1005006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae3c80082d7160cffb03bd466f033d6110e9030edbb2e03dbd45e98bc9028e17" } } ], "extra": [ 1, 213, 35, 247, 95, 233, 212, 63, 240, 168, 6, 184, 154, 143, 240, 61, 77, 142, 38, 254, 144, 157, 111, 104, 145, 86, 166, 26, 221, 62, 234, 107, 59, 2, 17, 0, 0, 0, 2, 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