Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef80b03a3e38cc6fe19e34d13996f13d80514f31502c591a0a40fdb5c348937c

Tx prefix hash: dfa20fc18ff2a9d261bff7677dacf6de562863f0b10dec8cb9928467d45bd75a
Tx public key: 4bf40ded58ae712a3428390eea6a03a0f41c3b3bdfac3de9b7caed74d7f3d1fe
Timestamp: 1725507574 Timestamp [UCT]: 2024-09-05 03:39:34 Age [y:d:h:m:s]: 00:238:11:28:33
Block: 1103219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170290 RingCT/type: yes/0
Extra: 014bf40ded58ae712a3428390eea6a03a0f41c3b3bdfac3de9b7caed74d7f3d1fe02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ec12b75461313dc308f151879f8f852c3900be26ea35a0cf9452d83211645f8 0.600000000000 1579960 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": 1103229, "vin": [ { "gen": { "height": 1103219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ec12b75461313dc308f151879f8f852c3900be26ea35a0cf9452d83211645f8" } } ], "extra": [ 1, 75, 244, 13, 237, 88, 174, 113, 42, 52, 40, 57, 14, 234, 106, 3, 160, 244, 28, 59, 59, 223, 172, 61, 233, 183, 202, 237, 116, 215, 243, 209, 254, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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