Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85be3b0cf5d6cd25fe5f8670b746c8b22440cc584f1f981c823f772e2ecd26ed

Tx prefix hash: 65d8f3c3edef96810420fb645f6f49a9286361bd6a53ecd9975f9dc49c3d62c9
Tx public key: 3f95df5f9000866e0723da3bea4db858057561e0c4a1ab72d8f1811ddacb4110
Timestamp: 1645369049 Timestamp [UCT]: 2022-02-20 14:57:29 Age [y:d:h:m:s]: 03:084:01:49:14
Block: 442698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 840175 RingCT/type: yes/0
Extra: 013f95df5f9000866e0723da3bea4db858057561e0c4a1ab72d8f1811ddacb411002110000001ebf7ee4e7000000000000000000

1 output(s) for total of 20.948746566000 dcy

stealth address amount amount idx
00: 65e39da27c8204dd3001eb20ad83edee8c7a53679f4270acfbf51020a2863140 20.948746566000 855549 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": 442708, "vin": [ { "gen": { "height": 442698 } } ], "vout": [ { "amount": 20948746566, "target": { "key": "65e39da27c8204dd3001eb20ad83edee8c7a53679f4270acfbf51020a2863140" } } ], "extra": [ 1, 63, 149, 223, 95, 144, 0, 134, 110, 7, 35, 218, 59, 234, 77, 184, 88, 5, 117, 97, 224, 196, 161, 171, 114, 216, 241, 129, 29, 218, 203, 65, 16, 2, 17, 0, 0, 0, 30, 191, 126, 228, 231, 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