Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29c6cdef630636c3315e10eee3685e1de9f498d7eb31db3e4f3630ceb64a5346

Tx prefix hash: 5675ff0b054a87a4e9f92f9595a6ea37cfd9092464bbc9de9f2f3acf9d4959ec
Tx public key: 22de3a435a19d329365dfa364038221e6d875ece21892206bae4a7a2a18856db
Timestamp: 1710424066 Timestamp [UCT]: 2024-03-14 13:47:46 Age [y:d:h:m:s]: 01:301:04:04:33
Block: 978188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474024 RingCT/type: yes/0
Extra: 0122de3a435a19d329365dfa364038221e6d875ece21892206bae4a7a2a18856db02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e1492c4743f3c1bad9e04d53c806bd86eea63ba12be10197a34cfc53a626d03 0.600000000000 1438207 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": 978198, "vin": [ { "gen": { "height": 978188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e1492c4743f3c1bad9e04d53c806bd86eea63ba12be10197a34cfc53a626d03" } } ], "extra": [ 1, 34, 222, 58, 67, 90, 25, 211, 41, 54, 93, 250, 54, 64, 56, 34, 30, 109, 135, 94, 206, 33, 137, 34, 6, 186, 228, 167, 162, 161, 136, 86, 219, 2, 17, 0, 0, 0, 12, 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