Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0646d20d92a1172559e8cebd4292616c2d65b47d49ba95d74532e86c37f5862

Tx prefix hash: 8dc3160bed5c67c68c59dcc98e9522458cad74c96f434c357a658ebd32bba2fb
Tx public key: b1c830b4f4c70618148988801572e3e80857d91cb70e24dcde6c51474ee9be74
Timestamp: 1694210724 Timestamp [UCT]: 2023-09-08 22:05:24 Age [y:d:h:m:s]: 01:145:00:29:59
Block: 843935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364715 RingCT/type: yes/0
Extra: 01b1c830b4f4c70618148988801572e3e80857d91cb70e24dcde6c51474ee9be7402110000000275e3f0e9000000000000000000

1 output(s) for total of 0.981054370000 dcy

stealth address amount amount idx
00: 61b221389a501b60277c1d4fb187ed0bce3df558cecff8d88b969cf4286cdb3f 0.981054370000 1297211 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": 843945, "vin": [ { "gen": { "height": 843935 } } ], "vout": [ { "amount": 981054370, "target": { "key": "61b221389a501b60277c1d4fb187ed0bce3df558cecff8d88b969cf4286cdb3f" } } ], "extra": [ 1, 177, 200, 48, 180, 244, 199, 6, 24, 20, 137, 136, 128, 21, 114, 227, 232, 8, 87, 217, 28, 183, 14, 36, 220, 222, 108, 81, 71, 78, 233, 190, 116, 2, 17, 0, 0, 0, 2, 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