Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0dad43e7eb8e3164e55e1371e1ebd20ffa2122d7ab5cbd32a0e11e27764136

Tx prefix hash: bf338c3ce1d33df1b7dce1e03e6aee0ba6812cac1e13f5f96342ec1f1421a3c3
Tx public key: 829518b988f9b66e945835280993aa09121c0199449b32adce5a89584fd824e5
Timestamp: 1700803789 Timestamp [UCT]: 2023-11-24 05:29:49 Age [y:d:h:m:s]: 01:069:05:22:34
Block: 898403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310620 RingCT/type: yes/0
Extra: 01829518b988f9b66e945835280993aa09121c0199449b32adce5a89584fd824e502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.647467393000 dcy

stealth address amount amount idx
00: f597f41e393100f6d8281cb4006d58d12436e2e2f2bbddd7dcac103bc4c26039 0.647467393000 1354816 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": 898413, "vin": [ { "gen": { "height": 898403 } } ], "vout": [ { "amount": 647467393, "target": { "key": "f597f41e393100f6d8281cb4006d58d12436e2e2f2bbddd7dcac103bc4c26039" } } ], "extra": [ 1, 130, 149, 24, 185, 136, 249, 182, 110, 148, 88, 53, 40, 9, 147, 170, 9, 18, 28, 1, 153, 68, 155, 50, 173, 206, 90, 137, 88, 79, 216, 36, 229, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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