Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 628aef2381d085efd6ec299c09f5a4c236368b60bbc3e959fcd5e3fbb58124b9

Tx prefix hash: c9b28de1c0045328191b2ff337198e41506c78fcdf4b7f41257098ee7ea4a2ce
Tx public key: fd9a3a2282eb11b0e9773c4d378405c7454e9e17e10553058eab4e9afbec2e4a
Timestamp: 1698301117 Timestamp [UCT]: 2023-10-26 06:18:37 Age [y:d:h:m:s]: 01:088:07:42:58
Block: 877879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324300 RingCT/type: yes/0
Extra: 01fd9a3a2282eb11b0e9773c4d378405c7454e9e17e10553058eab4e9afbec2e4a02110000000233af99f4000000000000000000

1 output(s) for total of 0.757220676000 dcy

stealth address amount amount idx
00: 46c37260334db20f9edf4ffbb5f9a28e3de72d9fad87fd39d23b719eadffb491 0.757220676000 1333273 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": 877889, "vin": [ { "gen": { "height": 877879 } } ], "vout": [ { "amount": 757220676, "target": { "key": "46c37260334db20f9edf4ffbb5f9a28e3de72d9fad87fd39d23b719eadffb491" } } ], "extra": [ 1, 253, 154, 58, 34, 130, 235, 17, 176, 233, 119, 60, 77, 55, 132, 5, 199, 69, 78, 158, 23, 225, 5, 83, 5, 142, 171, 78, 154, 251, 236, 46, 74, 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