Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2d7fd6a4881b22b1f687c0d32d6f24aa6f446c2e915b72b6f68c6efb3bcf91

Tx prefix hash: f81e4ebd411ea880cd81e560d5630b12c6a5345edb1b7ecbd03eb6b8bca09b86
Tx public key: 3ee2a799c9f6eb89334ab1f0be5d7961e6e593ddd33cd9c1ccd88fc2e5e7a307
Timestamp: 1727874151 Timestamp [UCT]: 2024-10-02 13:02:31 Age [y:d:h:m:s]: 01:043:11:06:00
Block: 1122837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289453 RingCT/type: yes/0
Extra: 013ee2a799c9f6eb89334ab1f0be5d7961e6e593ddd33cd9c1ccd88fc2e5e7a30702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf1b332346efeb6b243a165e8e3de074ed1957da6a4cf2fa63cc517601ba5e07 0.600000000000 1605370 of 15

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": 1122847, "vin": [ { "gen": { "height": 1122837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf1b332346efeb6b243a165e8e3de074ed1957da6a4cf2fa63cc517601ba5e07" } } ], "extra": [ 1, 62, 226, 167, 153, 201, 246, 235, 137, 51, 74, 177, 240, 190, 93, 121, 97, 230, 229, 147, 221, 211, 60, 217, 193, 204, 216, 143, 194, 229, 231, 163, 7, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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