Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2d9ad31c466cc74171115bbe4442798af33f4ae45366c4b81b67d47724055d

Tx prefix hash: 7fe098a0c508b37ba34c2014f942a4ab77f6b451830bd8ec9c704976583ebb50
Tx public key: 1f661dee2d6dc3bb026d1e91d08bfaa1eba5006103c534ecce3794daa6a3a2aa
Timestamp: 1714334076 Timestamp [UCT]: 2024-04-28 19:54:36 Age [y:d:h:m:s]: 00:305:03:06:08
Block: 1010573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218102 RingCT/type: yes/0
Extra: 011f661dee2d6dc3bb026d1e91d08bfaa1eba5006103c534ecce3794daa6a3a2aa02110000000559dad3f5000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 220bd3a427557c9f9ecb5d79dd961e33a90692944359ba260651857d6dc40b8a 0.615600000000 1472567 of 0

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": 1010583, "vin": [ { "gen": { "height": 1010573 } } ], "vout": [ { "amount": 615600000, "target": { "key": "220bd3a427557c9f9ecb5d79dd961e33a90692944359ba260651857d6dc40b8a" } } ], "extra": [ 1, 31, 102, 29, 238, 45, 109, 195, 187, 2, 109, 30, 145, 208, 139, 250, 161, 235, 165, 0, 97, 3, 197, 52, 236, 206, 55, 148, 218, 166, 163, 162, 170, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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