Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735eaa8b9b0f7ad7391bc192e66364e4c9fa43c475f59ecd9c12d860099a460c

Tx prefix hash: 0f633017b0ceec5eb06cf67795dee0b68a86b69a9d81e20c1e64c154e420839b
Tx public key: dc37567018cd5f078f2f5741d5a377e8115a895cab64e6333831d9d0774edc07
Timestamp: 1695399661 Timestamp [UCT]: 2023-09-22 16:21:01 Age [y:d:h:m:s]: 01:116:06:19:58
Block: 853798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344384 RingCT/type: yes/0
Extra: 01dc37567018cd5f078f2f5741d5a377e8115a895cab64e6333831d9d0774edc0702110000000933af99f4000000000000000000

1 output(s) for total of 0.909940193000 dcy

stealth address amount amount idx
00: 8799db56198538e754a5b002428ceac04476f982dfa09be962e50add9a59e380 0.909940193000 1307734 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": 853808, "vin": [ { "gen": { "height": 853798 } } ], "vout": [ { "amount": 909940193, "target": { "key": "8799db56198538e754a5b002428ceac04476f982dfa09be962e50add9a59e380" } } ], "extra": [ 1, 220, 55, 86, 112, 24, 205, 95, 7, 143, 47, 87, 65, 213, 163, 119, 232, 17, 90, 137, 92, 171, 100, 230, 51, 56, 49, 217, 208, 119, 78, 220, 7, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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