Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faad34e46afb98776052904abf45f2dd6a0f0c2555040785da9e637fa8e72a08

Tx prefix hash: 265dbb1fbb8f05ed8a03072d9ea61e16ce811426c9a4ed6f855a04bee3a8a8f9
Tx public key: ea9a6eadfed6530fcad19d4a500d41c08b2513c2323e901de80b28eccf4a8e93
Timestamp: 1704278596 Timestamp [UCT]: 2024-01-03 10:43:16 Age [y:d:h:m:s]: 01:162:17:37:20
Block: 927220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377369 RingCT/type: yes/0
Extra: 01ea9a6eadfed6530fcad19d4a500d41c08b2513c2323e901de80b28eccf4a8e930211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fccd2a9e182a6749dad1aa57dad0500f53fb67dacb9f004fed9d5f25de647f6f 0.600000000000 1385028 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": 927230, "vin": [ { "gen": { "height": 927220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fccd2a9e182a6749dad1aa57dad0500f53fb67dacb9f004fed9d5f25de647f6f" } } ], "extra": [ 1, 234, 154, 110, 173, 254, 214, 83, 15, 202, 209, 157, 74, 80, 13, 65, 192, 139, 37, 19, 194, 50, 62, 144, 29, 232, 11, 40, 236, 207, 74, 142, 147, 2, 17, 0, 0, 0, 4, 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