Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a09184255f6565e4275a7c456acb4c03ab42cd376700f853ea483f8d8a3463

Tx prefix hash: 4d9b8b1151af0f77e3a58478eb9c117cd4f95604afdb73e3386af5c96dfa9bd5
Tx public key: 6952971bc4ab3c45a219b98722e0332849bdc6d9a3736f1bca26230bf4bbc0f5
Timestamp: 1714468708 Timestamp [UCT]: 2024-04-30 09:18:28 Age [y:d:h:m:s]: 00:254:23:24:34
Block: 1011697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182500 RingCT/type: yes/0
Extra: 016952971bc4ab3c45a219b98722e0332849bdc6d9a3736f1bca26230bf4bbc0f50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08cab1b264514553e9e66191a37de47e21e0c688dcb939fc10c149e03324d209 0.600000000000 1473991 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": 1011707, "vin": [ { "gen": { "height": 1011697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08cab1b264514553e9e66191a37de47e21e0c688dcb939fc10c149e03324d209" } } ], "extra": [ 1, 105, 82, 151, 27, 196, 171, 60, 69, 162, 25, 185, 135, 34, 224, 51, 40, 73, 189, 198, 217, 163, 115, 111, 27, 202, 38, 35, 11, 244, 187, 192, 245, 2, 17, 0, 0, 0, 4, 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