Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677d179a553fd7ce6d9eef1f9efd60f40a0787558005314d296ae5aab28edd01

Tx prefix hash: 69487ee47c8c04d546481fba74ed737edd54c64248c58135d11a2d647d63091c
Tx public key: 8eec21f8542890ec4dc18de3d12764a35466b6169bde4aa247056afdee0ab41d
Timestamp: 1633294180 Timestamp [UCT]: 2021-10-03 20:49:40 Age [y:d:h:m:s]: 03:324:05:48:40
Block: 346030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1006363 RingCT/type: yes/0
Extra: 018eec21f8542890ec4dc18de3d12764a35466b6169bde4aa247056afdee0ab41d02110000001936fe6557000000000000000000

1 output(s) for total of 43.798515906000 dcy

stealth address amount amount idx
00: 4d5d80ea6d8e1f387dc297a3e1b5c0fd93e4a13d674574362e0d939dbc89cda6 43.798515906000 709682 of 0

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": 346040, "vin": [ { "gen": { "height": 346030 } } ], "vout": [ { "amount": 43798515906, "target": { "key": "4d5d80ea6d8e1f387dc297a3e1b5c0fd93e4a13d674574362e0d939dbc89cda6" } } ], "extra": [ 1, 142, 236, 33, 248, 84, 40, 144, 236, 77, 193, 141, 227, 209, 39, 100, 163, 84, 102, 182, 22, 155, 222, 74, 162, 71, 5, 106, 253, 238, 10, 180, 29, 2, 17, 0, 0, 0, 25, 54, 254, 101, 87, 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