Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c89bf016a2b0163383992482432ff8696711c191bd835b48357b047c57fd2080

Tx prefix hash: 754dfac2452aa76f3c78396339f5e2eca91fa081b5a6c9b60a30951b66f58489
Tx public key: c3bd6a7a7467d9f5f60417cea915a53fe8b9a6f952302fe4dd622f005ed1c2e6
Timestamp: 1715273162 Timestamp [UCT]: 2024-05-09 16:46:02 Age [y:d:h:m:s]: 00:259:08:44:57
Block: 1018374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185581 RingCT/type: yes/0
Extra: 01c3bd6a7a7467d9f5f60417cea915a53fe8b9a6f952302fe4dd622f005ed1c2e602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a0fe148eb70b2fe9bfd024cd84bd7f6da0448b0dfa073256758d2f9a4a4a33 0.600000000000 1482163 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": 1018384, "vin": [ { "gen": { "height": 1018374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a0fe148eb70b2fe9bfd024cd84bd7f6da0448b0dfa073256758d2f9a4a4a33" } } ], "extra": [ 1, 195, 189, 106, 122, 116, 103, 217, 245, 246, 4, 23, 206, 169, 21, 165, 63, 232, 185, 166, 249, 82, 48, 47, 228, 221, 98, 47, 0, 94, 209, 194, 230, 2, 17, 0, 0, 0, 1, 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