Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3639eb6eff317fae7a4817f83b20dfb6198fefbd76c020ffaaf12f58fcf3ce96

Tx prefix hash: 7e49b89428ae845d3d2c1ad8f1c67d33cd490c8b20f367a3fc1fde8babc8af98
Tx public key: 250efbcecb74839800d7603b89bce8c25e670c3415869b4c39d0f0e97a8c0e70
Timestamp: 1692693686 Timestamp [UCT]: 2023-08-22 08:41:26 Age [y:d:h:m:s]: 01:274:18:01:40
Block: 831338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457556 RingCT/type: yes/0
Extra: 01250efbcecb74839800d7603b89bce8c25e670c3415869b4c39d0f0e97a8c0e7002110000000b75e3f0e9000000000000000000

1 output(s) for total of 1.080020963000 dcy

stealth address amount amount idx
00: 354932d30b34b9778bcb2ca90f6da7411eff19f3415605ebab62981977f21e8c 1.080020963000 1283758 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": 831348, "vin": [ { "gen": { "height": 831338 } } ], "vout": [ { "amount": 1080020963, "target": { "key": "354932d30b34b9778bcb2ca90f6da7411eff19f3415605ebab62981977f21e8c" } } ], "extra": [ 1, 37, 14, 251, 206, 203, 116, 131, 152, 0, 215, 96, 59, 137, 188, 232, 194, 94, 103, 12, 52, 21, 134, 155, 76, 57, 208, 240, 233, 122, 140, 14, 112, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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