Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8454afcea9e9bbe67a9f38df3ab471e7159be813a4d40b07eb85ef5b3ed81583

Tx prefix hash: caa3f7a2776b88b66190eaaae5fd59e9d5cc926a049710baeb2daac57ef60fa3
Tx public key: 83a50a61e65e743b9e66faa0ea4a082dbd8052cfafb32a4cd4aa5af252b14554
Timestamp: 1710333126 Timestamp [UCT]: 2024-03-13 12:32:06 Age [y:d:h:m:s]: 01:240:14:42:23
Block: 977434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430650 RingCT/type: yes/0
Extra: 0183a50a61e65e743b9e66faa0ea4a082dbd8052cfafb32a4cd4aa5af252b145540211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e321e4d9fecf11cd0a0eb33d8f52bd72d439b9797f250869b4ca20d1a46083 0.600000000000 1437437 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": 977444, "vin": [ { "gen": { "height": 977434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e321e4d9fecf11cd0a0eb33d8f52bd72d439b9797f250869b4ca20d1a46083" } } ], "extra": [ 1, 131, 165, 10, 97, 230, 94, 116, 59, 158, 102, 250, 160, 234, 74, 8, 45, 189, 128, 82, 207, 175, 179, 42, 76, 212, 170, 90, 242, 82, 177, 69, 84, 2, 17, 0, 0, 0, 5, 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