Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b758a1328b64d4ddef22cf63745d332b51e04326690fac9036b1f68efc411193

Tx prefix hash: fbab4a2402d52181c92a41187d7dc63128e79edf65fbf081240f0446f70cc62e
Tx public key: 653a4d5b03fe4351a9f25470364104f8cb61d8416bdf835ce7fb15c908212f56
Timestamp: 1584506239 Timestamp [UCT]: 2020-03-18 04:37:19 Age [y:d:h:m:s]: 04:282:20:17:18
Block: 84555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097976 RingCT/type: yes/0
Extra: 01653a4d5b03fe4351a9f25470364104f8cb61d8416bdf835ce7fb15c908212f56021100000001c2c2f844000000000000000000

1 output(s) for total of 321.984501564000 dcy

stealth address amount amount idx
00: bf39ae1231a8bd142620aef203287d7f56b0aa7563388a704d4f66ce3a0380de 321.984501564000 153227 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": 84565, "vin": [ { "gen": { "height": 84555 } } ], "vout": [ { "amount": 321984501564, "target": { "key": "bf39ae1231a8bd142620aef203287d7f56b0aa7563388a704d4f66ce3a0380de" } } ], "extra": [ 1, 101, 58, 77, 91, 3, 254, 67, 81, 169, 242, 84, 112, 54, 65, 4, 248, 203, 97, 216, 65, 107, 223, 131, 92, 231, 251, 21, 201, 8, 33, 47, 86, 2, 17, 0, 0, 0, 1, 194, 194, 248, 68, 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