Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a31109fb349e355f7fd70214122ae7d15bb2573dd3a75c7d742cbf9db32cdb7

Tx prefix hash: d519bd7823fadd4b1243ca8f7dd079d5e47b4cf05040ad9e2434660c8d56d7fb
Tx public key: d4cfee821084e068d3b52705e8401805ef874ce103f823b96c79d13c01b0f632
Timestamp: 1717568586 Timestamp [UCT]: 2024-06-05 06:23:06 Age [y:d:h:m:s]: 01:009:04:19:58
Block: 1037403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267382 RingCT/type: yes/0
Extra: 01d4cfee821084e068d3b52705e8401805ef874ce103f823b96c79d13c01b0f63202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d7c664fb9b16de4c9131217126174c3f573ce907de5e9be2924b6e1dd269a8 0.600000000000 1505934 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": 1037413, "vin": [ { "gen": { "height": 1037403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d7c664fb9b16de4c9131217126174c3f573ce907de5e9be2924b6e1dd269a8" } } ], "extra": [ 1, 212, 207, 238, 130, 16, 132, 224, 104, 211, 181, 39, 5, 232, 64, 24, 5, 239, 135, 76, 225, 3, 248, 35, 185, 108, 121, 209, 60, 1, 176, 246, 50, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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