Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 690ea1873450cd20533c74f76194584a41ea81d79e70d184550d2cf15f28f205

Tx prefix hash: 5e8ce536d89dd4c4f5d81fc49c34eb414ad89cc8439d5d9510aac79178047dcc
Tx public key: bb3a62463318e40d4fba0d978f8c04a7c1d0e9776be19de49f96c7d299d9ee2a
Timestamp: 1705790763 Timestamp [UCT]: 2024-01-20 22:46:03 Age [y:d:h:m:s]: 01:088:08:36:13
Block: 939724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324265 RingCT/type: yes/0
Extra: 01bb3a62463318e40d4fba0d978f8c04a7c1d0e9776be19de49f96c7d299d9ee2a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e60699d0dde0bf9cfc72b74736dba84066ee145304d84fa18bbdba85a2888b83 0.600000000000 1397836 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": 939734, "vin": [ { "gen": { "height": 939724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e60699d0dde0bf9cfc72b74736dba84066ee145304d84fa18bbdba85a2888b83" } } ], "extra": [ 1, 187, 58, 98, 70, 51, 24, 228, 13, 79, 186, 13, 151, 143, 140, 4, 167, 193, 208, 233, 119, 107, 225, 157, 228, 159, 150, 199, 210, 153, 217, 238, 42, 2, 17, 0, 0, 0, 2, 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