Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce6871167a5d9a9c6998ad2fd0d3399b8ba2b998573f8f4b85819a875f85b6f

Tx prefix hash: 4a2b271b07aa0c4405d6d97fec43d1bd07df27b1c4939580924f180356922ece
Tx public key: 399785940edfb153ac1ba9ff249388b352d30509e3476d2f4c9cbed586bbd4dd
Timestamp: 1705808352 Timestamp [UCT]: 2024-01-21 03:39:12 Age [y:d:h:m:s]: 00:298:22:25:54
Block: 939864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214059 RingCT/type: yes/0
Extra: 01399785940edfb153ac1ba9ff249388b352d30509e3476d2f4c9cbed586bbd4dd0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c1d00794773700e46f948fdbbf2f3c092dfa6ff4935645dcbc352556f5a96f4 0.600000000000 1397998 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": 939874, "vin": [ { "gen": { "height": 939864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c1d00794773700e46f948fdbbf2f3c092dfa6ff4935645dcbc352556f5a96f4" } } ], "extra": [ 1, 57, 151, 133, 148, 14, 223, 177, 83, 172, 27, 169, 255, 36, 147, 136, 179, 82, 211, 5, 9, 227, 71, 109, 47, 76, 156, 190, 213, 134, 187, 212, 221, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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