Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e7ed1b76495920cb4556f3a218f8a6a01f2f814c97c530675ad36f9f40784af

Tx prefix hash: 0e224a5997432529035809fc55878376f491d562e8e0913b339f348ae2953321
Tx public key: 0c206b7748983baf8ac3664051ca9f30a9a307d43d77e3b7e8d5d545a9ff4966
Timestamp: 1734194996 Timestamp [UCT]: 2024-12-14 16:49:56 Age [y:d:h:m:s]: 00:093:17:35:00
Block: 1175144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66775 RingCT/type: yes/0
Extra: 010c206b7748983baf8ac3664051ca9f30a9a307d43d77e3b7e8d5d545a9ff49660211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57757a842ab41e651e0b5f761c053e7fdb50561bf5d486478ebaeaf1a646711b 0.600000000000 1661383 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": 1175154, "vin": [ { "gen": { "height": 1175144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57757a842ab41e651e0b5f761c053e7fdb50561bf5d486478ebaeaf1a646711b" } } ], "extra": [ 1, 12, 32, 107, 119, 72, 152, 59, 175, 138, 195, 102, 64, 81, 202, 159, 48, 169, 163, 7, 212, 61, 119, 227, 183, 232, 213, 213, 69, 169, 255, 73, 102, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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