Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b99e82c667d5c5129e583817948fa1ca944f18a52969f7a6a97cfe5c5e71c2

Tx prefix hash: d02efde548305ea343b596255a4123580e3ff2bb6645659da424bd60b179b377
Tx public key: 1234c2fb1d58519bbd78f89fa7db36c383c5ebc5e9e29763f9c82ecf0aa2a2dd
Timestamp: 1709485438 Timestamp [UCT]: 2024-03-03 17:03:58 Age [y:d:h:m:s]: 01:249:17:24:31
Block: 970388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437198 RingCT/type: yes/0
Extra: 011234c2fb1d58519bbd78f89fa7db36c383c5ebc5e9e29763f9c82ecf0aa2a2dd0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3885c1d8710a5a8f3316e35c4efb5557a2aceedcc384e00ee87cec95779a1cc 0.600000000000 1430241 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": 970398, "vin": [ { "gen": { "height": 970388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3885c1d8710a5a8f3316e35c4efb5557a2aceedcc384e00ee87cec95779a1cc" } } ], "extra": [ 1, 18, 52, 194, 251, 29, 88, 81, 155, 189, 120, 248, 159, 167, 219, 54, 195, 131, 197, 235, 197, 233, 226, 151, 99, 249, 200, 46, 207, 10, 162, 162, 221, 2, 17, 0, 0, 0, 4, 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