Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caa9e5c8c3fe66d1af510fb09103fe989822c0cae5936d433e2df3cc12f59345

Tx prefix hash: 5ce963a46345303c0e856e5a2168180ebd3a5b3083b0cb115676c7d703cffdc3
Tx public key: 08f8c468c3749dcee24524cafca5d0b555e35a373764e15acc64e4c9d3104a71
Timestamp: 1744514726 Timestamp [UCT]: 2025-04-13 03:25:26 Age [y:d:h:m:s]: 00:221:18:34:06
Block: 1260286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156232 RingCT/type: yes/0
Extra: 0108f8c468c3749dcee24524cafca5d0b555e35a373764e15acc64e4c9d3104a710211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bac6746da10f72ab993af5f303a3985961831c681753ecaada9d7829d7652ac 0.600000000000 1747441 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": 1260296, "vin": [ { "gen": { "height": 1260286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bac6746da10f72ab993af5f303a3985961831c681753ecaada9d7829d7652ac" } } ], "extra": [ 1, 8, 248, 196, 104, 195, 116, 157, 206, 226, 69, 36, 202, 252, 165, 208, 181, 85, 227, 90, 55, 55, 100, 225, 90, 204, 100, 228, 201, 211, 16, 74, 113, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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