Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6822237526111a90564c8902939b0dca81dfd7c78ac7b73dcc0b45d4ac08fb1f

Tx prefix hash: f0fad585d1450e68c7c021d762d858d659c306c3feb75ade02650aaa95a430bc
Tx public key: 1a401c177c032d01ae4a045726b6f9370e17b4d33c7a4ef9e5645b515038f0c9
Timestamp: 1636637903 Timestamp [UCT]: 2021-11-11 13:38:23 Age [y:d:h:m:s]: 03:046:03:36:05
Block: 372130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811586 RingCT/type: yes/0
Extra: 011a401c177c032d01ae4a045726b6f9370e17b4d33c7a4ef9e5645b515038f0c902110000000a745f00f8000000000000000000

1 output(s) for total of 35.890476366000 dcy

stealth address amount amount idx
00: ad25b95f7e0357f1b09b619ee801fbbb6bd6225b0c1c81172a06b56c47b96701 35.890476366000 753894 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": 372140, "vin": [ { "gen": { "height": 372130 } } ], "vout": [ { "amount": 35890476366, "target": { "key": "ad25b95f7e0357f1b09b619ee801fbbb6bd6225b0c1c81172a06b56c47b96701" } } ], "extra": [ 1, 26, 64, 28, 23, 124, 3, 45, 1, 174, 74, 4, 87, 38, 182, 249, 55, 14, 23, 180, 211, 60, 122, 78, 249, 229, 100, 91, 81, 80, 56, 240, 201, 2, 17, 0, 0, 0, 10, 116, 95, 0, 248, 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