Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779d5ac063fd41ca3962bf801d6a59171039f068fec1e83a27e574de8cf9f9a5

Tx prefix hash: 07d1a38cbb3c96cf7362ddb50e80edf5440cc38b3a748a07fbfd206d36412d7c
Tx public key: 17e49ed48aabd30c5980d86b60b0442e4c50f97b6730781f6ac276142b230ff8
Timestamp: 1713690914 Timestamp [UCT]: 2024-04-21 09:15:14 Age [y:d:h:m:s]: 00:206:01:12:43
Block: 1005250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147505 RingCT/type: yes/0
Extra: 0117e49ed48aabd30c5980d86b60b0442e4c50f97b6730781f6ac276142b230ff80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d5a143e94dee4eeeadd92c0721f445af81f127ae44e3cd54a1d7be14410b021 0.600000000000 1465836 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": 1005260, "vin": [ { "gen": { "height": 1005250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d5a143e94dee4eeeadd92c0721f445af81f127ae44e3cd54a1d7be14410b021" } } ], "extra": [ 1, 23, 228, 158, 212, 138, 171, 211, 12, 89, 128, 216, 107, 96, 176, 68, 46, 76, 80, 249, 123, 103, 48, 120, 31, 106, 194, 118, 20, 43, 35, 15, 248, 2, 17, 0, 0, 0, 3, 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