Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6fd282686bc8ca781aec7fca635d51316a24836578d62a055698136c678874

Tx prefix hash: 043467a562d1c4f439cda8dcc25c6fcaa2ea1a4044f27193271a65d088904d51
Tx public key: 92f9fa6afe87cb0fb34252a67825228df06b60031a8a758b4e0ef8f029339e62
Timestamp: 1707721013 Timestamp [UCT]: 2024-02-12 06:56:53 Age [y:d:h:m:s]: 01:063:07:24:27
Block: 955750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306291 RingCT/type: yes/0
Extra: 0192f9fa6afe87cb0fb34252a67825228df06b60031a8a758b4e0ef8f029339e6202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af29c2ee0fd41d6754e54482038534d1d94c57c52d59febf464efb8b5a60a7ef 0.600000000000 1415050 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": 955760, "vin": [ { "gen": { "height": 955750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af29c2ee0fd41d6754e54482038534d1d94c57c52d59febf464efb8b5a60a7ef" } } ], "extra": [ 1, 146, 249, 250, 106, 254, 135, 203, 15, 179, 66, 82, 166, 120, 37, 34, 141, 240, 107, 96, 3, 26, 138, 117, 139, 78, 14, 248, 240, 41, 51, 158, 98, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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