Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9688c8a99936c91d1a3c28e59913c50fd7d235114ef30f23330d4f1e8826a806

Tx prefix hash: 80658c28e156d8c86da148557ba5cf0e20ecb0f53a10382d9c4de813a2e78df2
Tx public key: 6d9ef2b5be051d646231f181fd0eed35dff7b6b8050228b2a8e5d4e9780c659a
Timestamp: 1574567657 Timestamp [UCT]: 2019-11-24 03:54:17 Age [y:d:h:m:s]: 05:043:23:37:24
Block: 16143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1174327 RingCT/type: yes/0
Extra: 016d9ef2b5be051d646231f181fd0eed35dff7b6b8050228b2a8e5d4e9780c659a021100000008f95225a5000000000000000000

1 output(s) for total of 542.640772358000 dcy

stealth address amount amount idx
00: fb0bcface30edba2f177f80b1fb95e6dc06f9db26fc3278d66c958a337a61904 542.640772358000 22357 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": 16153, "vin": [ { "gen": { "height": 16143 } } ], "vout": [ { "amount": 542640772358, "target": { "key": "fb0bcface30edba2f177f80b1fb95e6dc06f9db26fc3278d66c958a337a61904" } } ], "extra": [ 1, 109, 158, 242, 181, 190, 5, 29, 100, 98, 49, 241, 129, 253, 14, 237, 53, 223, 247, 182, 184, 5, 2, 40, 178, 168, 229, 212, 233, 120, 12, 101, 154, 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