Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a19f6f98dd5c80ee4a32e3791c9ed1bc54bc7e773570501ba7659bd747fd581

Tx prefix hash: 78c0967a43f5fa59958a67bb7ef182e1233be8bedd4a014a290bb09996cd4fd1
Tx public key: 718f8b69e8592dfdfed965d8931e01ac195b6ae8dd54451b613e5fff0367acdf
Timestamp: 1706452261 Timestamp [UCT]: 2024-01-28 14:31:01 Age [y:d:h:m:s]: 01:066:16:40:12
Block: 945205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308763 RingCT/type: yes/0
Extra: 01718f8b69e8592dfdfed965d8931e01ac195b6ae8dd54451b613e5fff0367acdf02110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808ebb2721859cd458adbba756a84707020515b8d3eae712c5b1149d9aa6aac0 0.600000000000 1403515 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": 945215, "vin": [ { "gen": { "height": 945205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808ebb2721859cd458adbba756a84707020515b8d3eae712c5b1149d9aa6aac0" } } ], "extra": [ 1, 113, 143, 139, 105, 232, 89, 45, 253, 254, 217, 101, 216, 147, 30, 1, 172, 25, 91, 106, 232, 221, 84, 69, 27, 97, 62, 95, 255, 3, 103, 172, 223, 2, 17, 0, 0, 0, 15, 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