Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d63daabd9553048f7d6428b0e85d8f0b24c958882d97292b2e57b0022366e38

Tx prefix hash: cad74a0a7f4b5ffd04a9011c192fcff6591414a701a02cc1beed2da50f2e3344
Tx public key: 5698f3507ca8c7cb4bdf5884269541784f724d4ae6b876fd30548f4e00fded20
Timestamp: 1707844056 Timestamp [UCT]: 2024-02-13 17:07:36 Age [y:d:h:m:s]: 01:052:08:09:56
Block: 956773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298442 RingCT/type: yes/0
Extra: 015698f3507ca8c7cb4bdf5884269541784f724d4ae6b876fd30548f4e00fded200211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35182d4967626a44cf6baff4df368bd02236aa09cb4cee29dd3bcb0c4a263a5d 0.600000000000 1416083 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": 956783, "vin": [ { "gen": { "height": 956773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35182d4967626a44cf6baff4df368bd02236aa09cb4cee29dd3bcb0c4a263a5d" } } ], "extra": [ 1, 86, 152, 243, 80, 124, 168, 199, 203, 75, 223, 88, 132, 38, 149, 65, 120, 79, 114, 77, 74, 230, 184, 118, 253, 48, 84, 143, 78, 0, 253, 237, 32, 2, 17, 0, 0, 0, 7, 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