Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c712695f40499da59c9bb5bee576d29b816a3343a4c0beb5bf78f83eeb805a

Tx prefix hash: 6f61c9caae1e75a96254a268f48e32db76539330209e3c7a9467403a161ae71c
Tx public key: 2aada6162b40498eb212eb396ee22cb54bc6b08c64f4496eedfd21efe862879e
Timestamp: 1735388666 Timestamp [UCT]: 2024-12-28 12:24:26 Age [y:d:h:m:s]: 00:117:12:48:45
Block: 1185006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83807 RingCT/type: yes/0
Extra: 012aada6162b40498eb212eb396ee22cb54bc6b08c64f4496eedfd21efe862879e02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02e70ef0d455ea0399ccae7d314455e6186c24830a069254bf1319a9cb931c12 0.600000000000 1671471 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": 1185016, "vin": [ { "gen": { "height": 1185006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02e70ef0d455ea0399ccae7d314455e6186c24830a069254bf1319a9cb931c12" } } ], "extra": [ 1, 42, 173, 166, 22, 43, 64, 73, 142, 178, 18, 235, 57, 110, 226, 44, 181, 75, 198, 176, 140, 100, 244, 73, 110, 237, 253, 33, 239, 232, 98, 135, 158, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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