Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4045c6b5c17feebd8370979f9b2f7b7dd041405d776e2de39315e269293de2f0

Tx prefix hash: d81d2e448f8b6b5ae02d5cc4defd3459125f70ccf9566d128ae9990e1c48a0c3
Tx public key: e7bad935ad72b087df4675015b32b600fade59e0c2ee56eaf29a6b3f79f7419a
Timestamp: 1696117188 Timestamp [UCT]: 2023-09-30 23:39:48 Age [y:d:h:m:s]: 01:200:06:15:12
Block: 859757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404187 RingCT/type: yes/0
Extra: 01e7bad935ad72b087df4675015b32b600fade59e0c2ee56eaf29a6b3f79f7419a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.869497223000 dcy

stealth address amount amount idx
00: c2b1c620fef35cf0473c256747f1207246c8c4b8a5fc9e3d76f3e84df39b3318 0.869497223000 1314001 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": 859767, "vin": [ { "gen": { "height": 859757 } } ], "vout": [ { "amount": 869497223, "target": { "key": "c2b1c620fef35cf0473c256747f1207246c8c4b8a5fc9e3d76f3e84df39b3318" } } ], "extra": [ 1, 231, 186, 217, 53, 173, 114, 176, 135, 223, 70, 117, 1, 91, 50, 182, 0, 250, 222, 89, 224, 194, 238, 86, 234, 242, 154, 107, 63, 121, 247, 65, 154, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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