Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a214acd1a673d0c4e29a28cee2a5e78c128c1c9f37e072272628c460c1f3c8

Tx prefix hash: 0b271f6307216f0c4b20cdf861492b77cf15ad6a0f4c98044cd5ab3680cee872
Tx public key: f0d4559d500897c5cc160dc78ae5a5e9c7b5495db2d2f67529451666544efb49
Timestamp: 1581825557 Timestamp [UCT]: 2020-02-16 03:59:17 Age [y:d:h:m:s]: 05:085:21:14:31
Block: 66188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214062 RingCT/type: yes/0
Extra: 01f0d4559d500897c5cc160dc78ae5a5e9c7b5495db2d2f67529451666544efb490211000000047adf42d3000000000000000000

1 output(s) for total of 370.418346966000 dcy

stealth address amount amount idx
00: a3d9265bd1f2f0d58134d9ef43550282f47abf4cc8c3bcc98dfe4866a42ceec7 370.418346966000 121851 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": 66198, "vin": [ { "gen": { "height": 66188 } } ], "vout": [ { "amount": 370418346966, "target": { "key": "a3d9265bd1f2f0d58134d9ef43550282f47abf4cc8c3bcc98dfe4866a42ceec7" } } ], "extra": [ 1, 240, 212, 85, 157, 80, 8, 151, 197, 204, 22, 13, 199, 138, 229, 165, 233, 199, 181, 73, 93, 178, 210, 246, 117, 41, 69, 22, 102, 84, 78, 251, 73, 2, 17, 0, 0, 0, 4, 122, 223, 66, 211, 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