Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfec5eaeef3a7f25db5b0ed19095bbf242f25ff71bdecfe7b604adb1e6670713

Tx prefix hash: b5de417c8a5f25d8870f04af73623d94f0c3ae35eeeabae727b0bb010def9c15
Tx public key: f509782cb40abd5c86a039437ae73dcaff157e4e35d820cbbe5fb337e8212db0
Timestamp: 1687335805 Timestamp [UCT]: 2023-06-21 08:23:25 Age [y:d:h:m:s]: 01:315:03:14:21
Block: 787006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486398 RingCT/type: yes/0
Extra: 01f509782cb40abd5c86a039437ae73dcaff157e4e35d820cbbe5fb337e8212db002110000000233af99f4000000000000000000

1 output(s) for total of 1.514685853000 dcy

stealth address amount amount idx
00: b2adc074578332de1c337a2a2e029e966f5ab9f0390021c2c7854d0e934238fa 1.514685853000 1237023 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": 787016, "vin": [ { "gen": { "height": 787006 } } ], "vout": [ { "amount": 1514685853, "target": { "key": "b2adc074578332de1c337a2a2e029e966f5ab9f0390021c2c7854d0e934238fa" } } ], "extra": [ 1, 245, 9, 120, 44, 180, 10, 189, 92, 134, 160, 57, 67, 122, 231, 61, 202, 255, 21, 126, 78, 53, 216, 32, 203, 190, 95, 179, 55, 232, 33, 45, 176, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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