Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30bff6186f9b3c0191b6c6cf61fa7815fb4547042fbcc2fb544b04ce340b4168

Tx prefix hash: 7bed0226a229f0088cd6acad716f4e12bdf1f60c4d70d1c11b448d5650d950ea
Tx public key: bcf11a1ebc17130a3d1d6d0423ce8ff848d68b9757695097c2e35f3fbad2f1d4
Timestamp: 1714122003 Timestamp [UCT]: 2024-04-26 09:00:03 Age [y:d:h:m:s]: 00:203:01:23:17
Block: 1008824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145359 RingCT/type: yes/0
Extra: 01bcf11a1ebc17130a3d1d6d0423ce8ff848d68b9757695097c2e35f3fbad2f1d402110000000318ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a736bc2b552fa38dad52974f92dae3a54b0f3f110aa86dd7548f35acd583fa8 0.600000000000 1470304 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": 1008834, "vin": [ { "gen": { "height": 1008824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a736bc2b552fa38dad52974f92dae3a54b0f3f110aa86dd7548f35acd583fa8" } } ], "extra": [ 1, 188, 241, 26, 30, 188, 23, 19, 10, 61, 29, 109, 4, 35, 206, 143, 248, 72, 214, 139, 151, 87, 105, 80, 151, 194, 227, 95, 63, 186, 210, 241, 212, 2, 17, 0, 0, 0, 3, 24, 236, 144, 96, 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