Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c6c51e7cc99e7edac892e05a6978964fc1e5d853c92cc869cb92627e098ccdc

Tx prefix hash: 86377acfa965a19c8343b6fa9001fc20c30e138bf48788a381985d01f18a4b5f
Tx public key: 239c5137a27744bcdf488ce0b45b6bba87ce5b6ee5b25b809fe2b2f4db68a461
Timestamp: 1713897072 Timestamp [UCT]: 2024-04-23 18:31:12 Age [y:d:h:m:s]: 00:307:11:26:43
Block: 1006960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219775 RingCT/type: yes/0
Extra: 01239c5137a27744bcdf488ce0b45b6bba87ce5b6ee5b25b809fe2b2f4db68a4610211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d755c4c28c34cc5ca58cd269f53478a816a4f15ee5690c11b00f3b8b1ac4d0b 0.600000000000 1468158 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": 1006970, "vin": [ { "gen": { "height": 1006960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d755c4c28c34cc5ca58cd269f53478a816a4f15ee5690c11b00f3b8b1ac4d0b" } } ], "extra": [ 1, 35, 156, 81, 55, 162, 119, 68, 188, 223, 72, 140, 224, 180, 91, 107, 186, 135, 206, 91, 110, 229, 178, 91, 128, 159, 226, 178, 244, 219, 104, 164, 97, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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