Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0b08bca018a19a0e43e15e793dab28202bd787efc04d4ed5d5e5f7536a2bed

Tx prefix hash: 588e749d343c9ff34e3311b739f76f0ca432608a024b24f831595e42ae22c1f6
Tx public key: 69af6a6a23c3987fff29c1027fdccecb40bafa4c3e66d16808301e9f7a1754a3
Timestamp: 1731240808 Timestamp [UCT]: 2024-11-10 12:13:28 Age [y:d:h:m:s]: 00:013:17:06:13
Block: 1150663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9808 RingCT/type: yes/0
Extra: 0169af6a6a23c3987fff29c1027fdccecb40bafa4c3e66d16808301e9f7a1754a30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d9f66575fa885458d3ec3f438ba16886ba0bfedba1085923638dc24e4d6b119 0.600000000000 1636034 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": 1150673, "vin": [ { "gen": { "height": 1150663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d9f66575fa885458d3ec3f438ba16886ba0bfedba1085923638dc24e4d6b119" } } ], "extra": [ 1, 105, 175, 106, 106, 35, 195, 152, 127, 255, 41, 193, 2, 127, 220, 206, 203, 64, 186, 250, 76, 62, 102, 209, 104, 8, 48, 30, 159, 122, 23, 84, 163, 2, 17, 0, 0, 0, 5, 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