Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e05c67243a43c75f8b01d7c4a2a42502a02f1b02fd5873de5fb0b0883de45d93

Tx prefix hash: 8547aa1bd55613ed4fe16c3a4a7e3aa8153859b3ff05ac5d610c51f2fc89e2bd
Tx public key: a9161626ef61bf71672bf1ad35a62c741de5392a09cfa0f43208b58e570e31c8
Timestamp: 1705890672 Timestamp [UCT]: 2024-01-22 02:31:12 Age [y:d:h:m:s]: 01:094:01:33:44
Block: 940542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328352 RingCT/type: yes/0
Extra: 01a9161626ef61bf71672bf1ad35a62c741de5392a09cfa0f43208b58e570e31c802110000001d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f839b23cd42234ede03a66fff8b4569492f1f31014dcae44ff60cccdea58ef76 0.600000000000 1398680 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": 940552, "vin": [ { "gen": { "height": 940542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f839b23cd42234ede03a66fff8b4569492f1f31014dcae44ff60cccdea58ef76" } } ], "extra": [ 1, 169, 22, 22, 38, 239, 97, 191, 113, 103, 43, 241, 173, 53, 166, 44, 116, 29, 229, 57, 42, 9, 207, 160, 244, 50, 8, 181, 142, 87, 14, 49, 200, 2, 17, 0, 0, 0, 29, 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