Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd9637b1ef475544c4190f474f7be8684450ab706761f00b0d19b941518de97

Tx prefix hash: ae0308290d90ab4c10d10fb19eadc11b7b00e4dce0a033496f7a94497d94be64
Tx public key: c0a6b8fc07b32d1fab2a4e615e210639d0546e2f06b8dcb318f8664672054906
Timestamp: 1716857771 Timestamp [UCT]: 2024-05-28 00:56:11 Age [y:d:h:m:s]: 00:318:00:56:25
Block: 1031515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227300 RingCT/type: yes/0
Extra: 01c0a6b8fc07b32d1fab2a4e615e210639d0546e2f06b8dcb318f866467205490602110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a134c71bed424ebaceedc7477bcf77b07f53bbf9be477e4ed51b8e45093ab61 0.600000000000 1499964 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": 1031525, "vin": [ { "gen": { "height": 1031515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a134c71bed424ebaceedc7477bcf77b07f53bbf9be477e4ed51b8e45093ab61" } } ], "extra": [ 1, 192, 166, 184, 252, 7, 179, 45, 31, 171, 42, 78, 97, 94, 33, 6, 57, 208, 84, 110, 47, 6, 184, 220, 179, 24, 248, 102, 70, 114, 5, 73, 6, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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