Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a5df812547b58857165a4043a2f0e43b9e7c5f3f708b0b1bb8bc261b291aef

Tx prefix hash: b092a187adc63c40cbf50feaaecf2353bb28eddd17b803054eba0220eca99c85
Tx public key: 7d238a0673b0949d56a6551eabfbaa8111eeeba463e0fc80fe3f4d20ba3b4685
Timestamp: 1734140439 Timestamp [UCT]: 2024-12-14 01:40:39 Age [y:d:h:m:s]: 00:112:04:38:22
Block: 1174695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79957 RingCT/type: yes/0
Extra: 017d238a0673b0949d56a6551eabfbaa8111eeeba463e0fc80fe3f4d20ba3b4685021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ceb88fdc320b77ff57c849167f35f7d5099b2002479ff6b0db8f77c0f1ceeed 0.600000000000 1660880 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": 1174705, "vin": [ { "gen": { "height": 1174695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ceb88fdc320b77ff57c849167f35f7d5099b2002479ff6b0db8f77c0f1ceeed" } } ], "extra": [ 1, 125, 35, 138, 6, 115, 176, 148, 157, 86, 166, 85, 30, 171, 251, 170, 129, 17, 238, 235, 164, 99, 224, 252, 128, 254, 63, 77, 32, 186, 59, 70, 133, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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