Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0362273f78037f9c2acd0c5bf161246d9ea064a31183a00969a1247d5704285

Tx prefix hash: 1c395b09482de2a515be21af89a03a6cdf4389013f6f70377a614d2e52c7719c
Tx public key: dbccb8bea18faa7f4a565674d6564ac6cae379e840aa1d34a2a8183720830dce
Timestamp: 1699801475 Timestamp [UCT]: 2023-11-12 15:04:35 Age [y:d:h:m:s]: 01:080:07:48:40
Block: 890103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318558 RingCT/type: yes/0
Extra: 01dbccb8bea18faa7f4a565674d6564ac6cae379e840aa1d34a2a8183720830dce021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.689793757000 dcy

stealth address amount amount idx
00: 27e34e4bfa3bcd66847f9e6fc803550ba7eddddad185a0ce2c60da5fa28803a9 0.689793757000 1346122 of 0

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": 890113, "vin": [ { "gen": { "height": 890103 } } ], "vout": [ { "amount": 689793757, "target": { "key": "27e34e4bfa3bcd66847f9e6fc803550ba7eddddad185a0ce2c60da5fa28803a9" } } ], "extra": [ 1, 219, 204, 184, 190, 161, 143, 170, 127, 74, 86, 86, 116, 214, 86, 74, 198, 202, 227, 121, 232, 64, 170, 29, 52, 162, 168, 24, 55, 32, 131, 13, 206, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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