Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c820582aad0a05b854989475f41336e00a180ddce1ae963708706a92081d762

Tx prefix hash: 76ec5b3ed7504447986cda9ad387297521e451924d070d125ad93854ae0c968e
Tx public key: 289713f1256a4454f08ddc25bd6aa4f1551844a9d5b5c6d4474cddfcc1d261e0
Timestamp: 1714409270 Timestamp [UCT]: 2024-04-29 16:47:50 Age [y:d:h:m:s]: 00:303:20:43:21
Block: 1011203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217194 RingCT/type: yes/0
Extra: 01289713f1256a4454f08ddc25bd6aa4f1551844a9d5b5c6d4474cddfcc1d261e00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbbf7de162dae7fa1a4d2ee2d5e460353004fb7408092c88b5f456da2be3e8f3 0.600000000000 1473371 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": 1011213, "vin": [ { "gen": { "height": 1011203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbbf7de162dae7fa1a4d2ee2d5e460353004fb7408092c88b5f456da2be3e8f3" } } ], "extra": [ 1, 40, 151, 19, 241, 37, 106, 68, 84, 240, 141, 220, 37, 189, 106, 164, 241, 85, 24, 68, 169, 213, 181, 198, 212, 71, 76, 221, 252, 193, 210, 97, 224, 2, 17, 0, 0, 0, 1, 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