Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7ac047512f56d40a0477388ffcaf35576ee083c787d32ae7f0ec6e40065efa

Tx prefix hash: db923a2417025063a23582f008ce8f992d11197ec1ff64a58416232faba5a4c1
Tx public key: d9e2f5a39e2875bd0cd3db4aef6d1a6a3ef948254a7cccf28ab6e6d1d95941a2
Timestamp: 1713908735 Timestamp [UCT]: 2024-04-23 21:45:35 Age [y:d:h:m:s]: 00:345:14:40:25
Block: 1007057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247065 RingCT/type: yes/0
Extra: 01d9e2f5a39e2875bd0cd3db4aef6d1a6a3ef948254a7cccf28ab6e6d1d95941a20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1778e564c26fa28e20058ee0f05a65b1bfb3a4182875b98992d9ded195d59bae 0.600000000000 1468279 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": 1007067, "vin": [ { "gen": { "height": 1007057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1778e564c26fa28e20058ee0f05a65b1bfb3a4182875b98992d9ded195d59bae" } } ], "extra": [ 1, 217, 226, 245, 163, 158, 40, 117, 189, 12, 211, 219, 74, 239, 109, 26, 106, 62, 249, 72, 37, 74, 124, 204, 242, 138, 182, 230, 209, 217, 89, 65, 162, 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