Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fb280d7048e8490a008561073b4ca27ae58d3fabc925c9f3f71f2d45b742561

Tx prefix hash: e3d02800c1ebfa3d738f1b858763e002b105fe5de343ba31299bb0ebb736d84c
Tx public key: b0ea183af2fb2da2d37672caf6ade3ea4d17629fb810381b6377035cae3dce7b
Timestamp: 1699683536 Timestamp [UCT]: 2023-11-11 06:18:56 Age [y:d:h:m:s]: 01:058:12:33:59
Block: 889125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303230 RingCT/type: yes/0
Extra: 01b0ea183af2fb2da2d37672caf6ade3ea4d17629fb810381b6377035cae3dce7b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.694959956000 dcy

stealth address amount amount idx
00: fd58609762d28e26556b9e367ae895ffddbfc813b7684be121d24d2214bceb88 0.694959956000 1345102 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": 889135, "vin": [ { "gen": { "height": 889125 } } ], "vout": [ { "amount": 694959956, "target": { "key": "fd58609762d28e26556b9e367ae895ffddbfc813b7684be121d24d2214bceb88" } } ], "extra": [ 1, 176, 234, 24, 58, 242, 251, 45, 162, 211, 118, 114, 202, 246, 173, 227, 234, 77, 23, 98, 159, 184, 16, 56, 27, 99, 119, 3, 92, 174, 61, 206, 123, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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