Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1385fa63ee719869cbefe94dd7c2093efc7f0fc38c7f4d89f54e984491741503

Tx prefix hash: f43dc8f127e8415207a188cca1a0b3ec1caf5b58b81c3e02854d4323bca4614a
Tx public key: ab449a34c8736ec9fb8b5506fc6cf44e82540bef1a9782ef7213419b1322b69d
Timestamp: 1574560557 Timestamp [UCT]: 2019-11-24 01:55:57 Age [y:d:h:m:s]: 05:092:02:47:05
Block: 16083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1208466 RingCT/type: yes/0
Extra: 01ab449a34c8736ec9fb8b5506fc6cf44e82540bef1a9782ef7213419b1322b69d021100000008f95225a5000000000000000000

1 output(s) for total of 542.889231402000 dcy

stealth address amount amount idx
00: a0b5187197d40f9a70ef1f55f17b3d21ea1c7057b330d57d16633f5e03552bd4 542.889231402000 22219 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": 16093, "vin": [ { "gen": { "height": 16083 } } ], "vout": [ { "amount": 542889231402, "target": { "key": "a0b5187197d40f9a70ef1f55f17b3d21ea1c7057b330d57d16633f5e03552bd4" } } ], "extra": [ 1, 171, 68, 154, 52, 200, 115, 110, 201, 251, 139, 85, 6, 252, 108, 244, 78, 130, 84, 11, 239, 26, 151, 130, 239, 114, 19, 65, 155, 19, 34, 182, 157, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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