Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 806353fb0b408f1becbdfaab127b3bf809b1f95be468e51a447af06b9afd2084

Tx prefix hash: 02048b6c96801fec8805a2f60665f40d075a906cda9f6a52cf1cbc36214bd4c8
Tx public key: 9d3e26ea5073dd101b1115e7683ae026a288ad449f4102e4c3c12b4e6628361b
Timestamp: 1708710810 Timestamp [UCT]: 2024-02-23 17:53:30 Age [y:d:h:m:s]: 01:042:23:55:12
Block: 963962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291740 RingCT/type: yes/0
Extra: 019d3e26ea5073dd101b1115e7683ae026a288ad449f4102e4c3c12b4e6628361b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aab47de53cdb68d80d9193a727a1947436e3eb9d61181dd5ca474fa9677dc7e 0.600000000000 1423689 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": 963972, "vin": [ { "gen": { "height": 963962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aab47de53cdb68d80d9193a727a1947436e3eb9d61181dd5ca474fa9677dc7e" } } ], "extra": [ 1, 157, 62, 38, 234, 80, 115, 221, 16, 27, 17, 21, 231, 104, 58, 224, 38, 162, 136, 173, 68, 159, 65, 2, 228, 195, 193, 43, 78, 102, 40, 54, 27, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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